-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR: Do not launch Spyder if installing in CI or batch/silent mode (Installers) #22876
Conversation
6bdec89
to
c10c87a
Compare
@ccordoba12, we can include this in 6.0.3 since this does not require an update to |
Ok, I think that's a good idea.
Agreed. But to make this feature more discoverable, could you add a new entry to the FAQ page in our docs to describe how to install Spyder in silent mode? You can add a simple text about that and copy/paste the commands you posted in the OP. Then you could update that entry when 6.1 is released to delete |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of tiny suggestions for you @mrclary, the rest looks good to me.
With conda/constructor#885, batch/silent mode installs will automatically set INSTALLER_UNATTENDED environment variable accessible by user scripts. Until the next constructor version (>3.9.3) users may set either CI=1 or INSTALLER_UNATTENDED=1 at the commandline.
Co-authored-by: Carlos Cordoba <[email protected]>
2d944f5
to
3940d5d
Compare
I'm unable to make any commits to my local stdout
|
It also seems that we need to update the docs for 6.0 as well. |
Please open a new issue about that in Spyder-docs and assign it to CAM.
Right, we can only add the FAQ entry I mentioned once we update the docs for 6.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mrclary!
@meeseeksdev please backport to 6.x |
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the If these instructions are inaccurate, feel free to suggest an improvement. |
…in CI or batch/silent mode (Installers)
…ing in CI or batch/silent mode (Installers)) (#22893)
Description of Changes
Installing Spyder using our conda-based installers from the command-line will now recognize two environment variables:
CI
orINSTALLER_UNATTENDED
. If either are set to 1, Spyder will not be launched upon completing the installation.macOS
.pkg
installers do not receive command-line environment variables, soCI
andINSTALLER_UNATTENDED
will not have any affect. However,COMMAND_LINE_INSTALL
is unique to macOS.pkg
installers and set when launched from the command-line, so this variable is leveraged to refrain from launching Spyder in this circumstance.Note that for the next
constructor
release (>3.9.3, see conda/constructor#885),INSTALLER_UNATTENDED
is automatically set to 1 if.sh
or.exe
installers are run in batch mode (-b
for.sh
installers) or silent mode (/S
for.exe
installers).Examples
Issue(s) Resolved
Fixes #22730